
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
PowerBuilder Runtime Packager</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="apptechp244.htm">Previous</A>&nbsp;&nbsp;<A HREF="apptechp246.htm" >Next</A>
<!-- End Header -->
<A NAME="BAJDBEAB"></A><h1>PowerBuilder Runtime Packager</h1>
<A NAME="TI6835"></A><p>The PowerBuilder Runtime
Packager is a tool that packages the PowerBuilder files an application
needs at runtime into a Microsoft Windows Installer (MSI) package
file. Windows Installer is an installation and configuration service
that is installed with more recent Microsoft Windows operating systems.</p>
<A NAME="TI6836"></A><p>You can use the MSI file generated by the Runtime Packager
as part of an installation package that includes the other files
that your application needs.</p>
<A NAME="TI6837"></A><p>You must have Microsoft Windows Installer on your system in
order to run the Runtime Packager successfully. The Installer is always available
on Windows XP and Windows 2003.</p>
<A NAME="TI6838"></A><p>To get more information and to obtain the latest version of
Windows Installer, see the <A HREF="http://msdn.microsoft.com/en-us/default.aspx">Microsoft documentation</A>
.</p>
<A NAME="TI6839"></A><p>The Runtime Packager can be used with client applications
installed on Windows systems and applications deployed to the .NET
Framework. It does not package the files required if your application
uses the DataWindow Web control for ActiveX, and it does not install
most third-party components. See <A HREF="apptechp246.htm#CHDHHJGD">"Third-party components and
deployment"</A> for more information.</p>
<A NAME="TI6840"></A><p>Make sure that you read the sections referenced in <A HREF="apptechp244.htm#BAJBIECB">Table 37-2</A> that apply
to your application for more information about where files that
are not installed by the Runtime Packager should be installed.</p>
<A NAME="TI6841"></A><p><img src="images/proc.gif" width=17 height=17 border=0 align="bottom" alt="Steps"> To use the PowerBuilder Runtime Packager:</p>
<ol><li class=fi><p>Select Programs&gt;Sybase&gt;PowerBuilder
11.5&gt;PowerBuilder Runtime Packager from the Windows Start
menu or launch the <b>pbpack115</b> executable file
in your <i>Shared\PowerBuilder</i> directory. </p><br><img src="images/pbpack01.gif"><br>
</li>
<li class=ds><p>Select a location for the generated MSI file.</p></li>
<li class=ds><p>If you are deploying a .NET target, select PowerBuilder
.NET Components. Otherwise, select PowerBuilder Standard Components.</p></li>
<li class=ds><p>Select the database interfaces your application
requires.</p><p>The DLLs for the database interfaces you select are added
to the package. For ODBC and OLE DB, the <i>pbodb115.ini</i> file
is also added. For JDBC, the <i>pbjdbc12115.jar</i> and <i>pbjvm115.dll </i>files
are also added. The Java Runtime Environment (JRE) is <i>not</i> added.
See <A HREF="apptechp246.htm#CHDHHJGD">"Third-party components and
deployment"</A>.</p><p>Other ODBC or OLE DB files your application may require are
not added. For information about deploying these files, see <A HREF="apptechp248.htm#BGBCBACD">"ODBC database drivers and
supporting files"</A> and <A HREF="apptechp248.htm#BGBCFFEH">"OLE DB database providers"</A>. </p></li>
<li class=ds><p>If your application uses DataWindow XML export
or import or XML Web DataWindows, check the XML support check box.</p><p>The Runtime Packager adds <i>PBXerces115.dll</i>, <i>xerces-c_2_6.dll</i>,
and <i>xerces-depdom_2_6.dll</i>. </p></li>
<li class=ds><p>If your application uses the XML services provided
by the PowerBuilder Document Object Model or if it is an EJB or
SOAP Web services client, select the appropriate check boxes.</p><p>The Runtime Packager adds the DLLs, PBXs, and JAR files required
to the package. The Runtime Packager adds required files for both
the EasySoap and .NET Web service engines when you select the SOAP Client
for Web Service check box. For more information about required files
for these services, see <A HREF="apptechp250.htm#BAJHJBBB">"PowerBuilder extensions"</A>. </p><p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Web service DataWindows</span> <A NAME="TI6842"></A>You can also check the SOAP Client for Web Service box if
your application uses Web service DataWindows. Two of the files
added when you check this box, <i>Sybase.PowerBuilder.WebService.Runtime.dll</i> and <i>Sybase.PowerBuilder.WebService.Runtime.RemoteLoader.dll</i>,
are also required for Web service DataWindows.</p>
</li>
<li class=ds><p>If your application uses a rich text control or
DataWindow, select the Rich Text Support check box.</p><p>The Runtime Packager installs the files listed for Rich Text
support in <A HREF="apptechp247.htm#BAJFAHDA">Table 37-5</A></p></li>
<li class=ds><p>Click Create.</p><p>The Runtime Packager creates an MSI file that includes the
files required by the components you selected, as well as the runtime
DLLs for standard PowerBuilder applications or the runtime DLLs
and .NET assemblies for PowerBuilder .NET applications listed in <A HREF="apptechp245.htm#CHDEDABE">Table 37-3</A>.</p><A NAME="CHDEDABE"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-3: Base components</caption>
<tr><th  rowspan="1"  ><A NAME="TI6843"></A>Base components selected</th>
<th  rowspan="1"  ><A NAME="TI6844"></A>Files</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6845"></A>PowerBuilder Standard Components</td>
<td  rowspan="1"  ><A NAME="TI6846"></A><A NAME="TI6847"></A>
<ul>
<li class=fi><i>libjcc.dll</i></li>
<li class=ds><i>libjutils.dll</i></li>
<li class=ds><i>pbacc115.dll</i></li>
<li class=ds><i>pbcomrt115.dll</i></li>
<li class=ds><i>pbdpl115.dll</i></li>
<li class=ds><i>pbdwe115.dll</i></li>
<li class=ds><i>pbdwr115.dll</i></li>
<li class=ds><i>pbdwr115.pbd</i></li>
<li class=ds><i>pbjag115.dll</i></li>
<li class=ds><i>pbjvm115.dll</i></li>
<li class=ds><i>pbshr115.dll</i></li>
<li class=ds><i>pbtra115.dll</i></li>
<li class=ds><i>pbtrs115.dll</i></li>
<li class=ds><i>pbvm115.dll</i>
</li>
</ul>
</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6848"></A>PowerBuilder .NET components</td>
<td  rowspan="1"  ><A NAME="TI6849"></A><A NAME="TI6850"></A>
<ul>
<li class=fi><i>pbdpl115.dll</i></li>
<li class=ds><i>pbshr115.dll</i></li>
<li class=ds><i>pbrth115.dll</i></li>
<li class=ds><i>pbdwm115.dll</i>
</li>
</ul>
<A NAME="TI6851"></A><p>PowerBuilder .NET assemblies:<A NAME="TI6852"></A>
<ul>
<li class=fi><i>Sybase.PowerBuilder.ADO.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Common.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Core.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Datawindow.Web.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.DataWindow.Win.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Datawindow.Interop.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Db.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.DBExt.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.EditMask.Win.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.EditMask.Interop.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Graph.Web.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Graph.Win.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Graph.Core.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Graph.Interop.dll</i></li>
<li class=ds>Sybase.PowerBuilder.<i>RTC.Win.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.RTC.Interop.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Interop.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Web.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Web.WebService.dll</i></li>
<li class=ds><i>Sybase.Powerbuilder.WebService.Runtime.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll</i></li>
<li class=ds><i>Sybase.PowerBuilder.Win.dll</i>
</li>
</ul>
</p></td>
</tr>
</table>
</li></ol>
<br><A NAME="TI6853"></A><p>The MSI file is a compressed file that can be executed directly
on any Windows platform. It registers any self-registering DLLs,
adds the installation destination path to the Windows Registry,
sets the system PATH environment variable, and adds information
to the Registry for the Install/Uninstall page in the Windows
Control Panel. It can also be used in some third-party installation software
packages.</p>
<A NAME="TI6854"></A><p>For .NET applications, the MSI file installs the .NET assemblies
into the Global Assembly Cache (GAC). The .NET Framework 2.0 must
be installed on the target computer. If it is not, the installation
stops and an error message displays. If the IE Web Controls required
for .NET Web Forms targets are not installed, a warning message
displays but installation continues. After you run the MSI file
on a production server for .NET Web Forms applications or Web services,
or on a client computer for .NET Windows Forms or smart client applications,
you must restart the target system.</p>
<A NAME="TI6855"></A><p>For more information about deploying .NET targets, see the
first chapter in <i>Deploying Applications and Components
to .NET</i>
.</p>

